home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_1199
/
1035
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
2KB
From: Wolfgang Zweygart <wz@echo.chem.TU-Berlin.DE>
Subject: Re: Shortcut file
Date: Tue, 26 Jul 94 18:19:03 MESZ
In-Reply-To: <199407260740.AA18579@world.std.com>; from "C.J.Ridd@computer-science.birmingham.ac.uk" at Jul 26, 94 8:39 am
Mailer: Elm [revision: 70.85]
Precedence: bulk
Hi out there..
> (Trying to steer the discussion back on track!)
good idea,
> Will there be only one global file, or one file per application? Using
> one file for 'normal' shortcuts (Open, Quit etc etc) would be useful,
> and the application-specific file could have extra information in it
> for that app only, like license keys, or any settings information that
> is needed.
I would suggest a general file.
with some application specific extra information appended to it.
Here is an example:
OPEN ^O 24
CLOSE ^U 28
CYCLE ^W 29
ABCD_FIND F 'F
ABCD_CHANGE C 'C
So first field will be the name of the function, for example OPEN for
opening what ever. Second field shows what should appear in the menu-bar
and third field is the keycode refereing to it. The application
specific codes may start with the short name of the application
(here ABCD) followed by the specific function.
> Will it (they) be in a standard directory, or pointed to by an
> environment variable? Suggestion: locate the file(s) using shel_find()
> if possible, then an environment variable if possible, then a specific
> directory if possible.
This new system should work even for a total beginner starting with an
Atari and this new application without any Install program.
So the program has to find it and interpret it at start.
Bye Wolfgang, just my 2 Pf.
--
Wolfgang Zweygart
wz@echo.chem.tu-berlin.de
wz2@pauli-p2.physik.uni-stuttgart.de
Fidonet.org 2:246/1104.0
Turbonet.ftn 100:11/0.0
Gernet.ftn 21:492/1414.0